server caching - new baseline not visible until server restarts

Imagine I would be able to extract a baseline from a module A and create a new module B from it, make some changes to that newly created module B, and then merge it back into module A as a new baseline - on database level, that is directly manipulating the V6DATA files.

Doing something similar I find that the changes will not be displayed in DOORS unless I restart the DOORS server. It seems like the DOORS server has some internal cache that will not recognize the new baseline until I restarted the server.

Anyone had a similar problem of changes to V6DATA not "going live" until the server was restarted? Is there a better way to make the server clear its internal cache or whatever is responsible for that? Maybe you backup experts know a solution for that?

Regards, Mathias